Skip to content

Tech/magma#1

Open
andrea-ferretti wants to merge 10 commits intoblmelp:valencia_magmafrom
yambo-code:tech/magma
Open

Tech/magma#1
andrea-ferretti wants to merge 10 commits intoblmelp:valencia_magmafrom
yambo-code:tech/magma

Conversation

@andrea-ferretti
Copy link

No description provided.

nicspalla and others added 9 commits March 22, 2023 10:28
    MODIFIED *  include/driver/version.h dipoles/DIPOLE_overlaps.F

    NEW *

    Bugs:
    - workaround for issue #729 to fix compilation

    Patch sent by:  Davide Sangalli <davide.sangalli@gmail.com>
Conflicts:
	config/report.in
	include/driver/version.h
	src/modules/.objects
@sangallidavide sangallidavide deleted the tech/magma branch January 15, 2024 09:52
complex(c_float_complex), target :: A(lda,*)
real(c_double), target :: w(*)
complex(c_float_complex), target :: work(*)
real(c_double), target :: rwork(*)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the MAGMA Fortran stubs w and rwork are float, not double. Any reason they are double in here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,
you are right, this looks like a mistake... [ I haven't written the modules myself, but generated from magma-2.7.1 using a codegen.py script (only the z version is there)... Here the point is that the script is no longer distributed with this version of magma and I've downloaded a previous version... ]

nevertheless, you are right and this needs to be fixed !
I've attempted a fix here: 20369f3

@blmelp
Copy link
Owner

blmelp commented Jan 30, 2024

I was trying to test this branch and add our part of the code over it.

  • About the configuration: It detected MAGMA as an external library, but the linker was missing links to cusparse and stdc++. I am using MAGMA v2.7.1.
  • I tried to run some test on your branch and it gave segmentation fault. Not sure why, but it happens also when trying to run just yambo -v. Do you know why this may happen?
  • I added some comment on the code. I could compile my code over yours but there were some differences on the interface of the Fortran stub.

@sangallidavide sangallidavide restored the tech/magma branch February 5, 2024 09:51
@andrea-ferretti
Copy link
Author

Concerning these last comments:

  • which compiler are you using to build yambo ? (I think in my tests I must have used the nvidia sdk)
  • the fact that yambo -v does not work seems reasonably to point to compilation problem (library clash ?)

cat > conftest.$ac_ext <<_ACEOF
program main

use magma
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this test needed? I think MAGMA Fortran stubs are not needed since the ones defined in Yambo are the ones that are used. In theory you could link a MAGMA library compiled without Fortran.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I was giving it another try.

  • I am also using the nvidia sdk
  • Apparently there is some conflict, at least in my case, when you have the Fortran stubs from MAGMA and also from Yambo. I was able to compile it using a MAGMA library without Fortran stubs. However I needed to comment this test in the configure to be able to do so. Have you tested this with a MAGMA library with Fortran stubs?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Blanca, thanks for reporting... we'll run the tests ASAP and let you know

@sangallidavide sangallidavide deleted the tech/magma branch June 21, 2024 09:31
@sangallidavide
Copy link

@blmelp
Sorry for the long silence.
Today we came back looking into the status of our interface with the magma libraries. We decided to import in our branch ( yambo-code/yambo/tech-magma ) the developments present inside the branch valencia_magma (we will eventually work on top of it to finalize the development ).

Was there anything else we should consider on your side and related to magma, or everything was in the valencia_magma branch?

@blmelp
Copy link
Owner

blmelp commented Oct 14, 2024

Everything from our side is on the valencia_magma branch, but using the MAGMA Fortran stubs. I tried to run a test with our code over the Yambo Fortran stubs for MAGMA (on a local branch), and ran into some problems that we discussed in this thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants